This PR resolves the inconsistency between SdkLogger and SdkTracer by adding Clone implementation to SdkLogger.

Problem

Currently, SdkTracer implements Clone but SdkLogger does not, creating an inconsistent API experience:

// SdkTracer can be cloned
let tracer = tracer_provider.tracer("my-tracer");
let cloned_tracer = tracer.clone(); // ✅ Works

// SdkLogger cannot be cloned
let logger = logger_provider.logger("my-logger"); 
let cloned_logger = logger.clone(); // ❌ Compilation error

This forces users to wrap SdkLogger in Arc or similar constructs when they need to share it across multiple contexts.

Solution

Added Clone to the derive macro for SdkLogger. This is safe because both fields in the struct already implement Clone:

• InstrumentationScope implements Clone
• SdkLoggerProvider implements Clone

Changes

• Modified SdkLogger from #[derive(Debug)] to #[derive(Debug, Clone)]
• Added a test to verify the Clone functionality works correctly

After this change

// Both now work consistently
let tracer = tracer_provider.tracer("my-tracer");
let cloned_tracer = tracer.clone(); // ✅ Works

let logger = logger_provider.logger("my-logger"); 
let cloned_logger = logger.clone(); // ✅ Now works too!

This is a non-breaking change that improves API consistency and developer experience.

Fixes #3058.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.